Subject: BobC's Note - LocalTgPortName

From: "Leo Temoshenko" <[email-masked]>
Date: Wed, 25 Oct 95 10:08:14 EDT

Hi,
>From an implementors (and architectural) standpoint, port name should
NOT be in the LocalTgTable.

o The local tg table is currently used to get local topo from trs.
  - Port name is NOT in the trs data base.
  - I do not believe port name is needed to "draw" local topo; and
    doubt that level of detail could be shown.
o BobC's "how do we convey this info" comment
  - Relating a local tg (which is indexed by tg num and dest name)
    can be done by using the link table.  The link table is indexed
    by link name; and contains the port name, tg num and dest name
    regardless of whether the tg is active or not.  Note that
    the local tg table (from trs) will only have an entry if
    the tg is active.
o BobC's "we use two components elsewhere" comment
  - True, CS and DLCx are used to create several tables.
    HOWEVER the info is a direct one-to-one match (for example
    link station info); and the components are intimately related
    (cs knows some link info and dlcx knows some link info - neither
    knows all); and there is NO lookup/seaching.
  - A TRS-CS combination is not at all similar.
o The effort to accomplish this (if someone really wanted to) is
  about the same for the manager as for the agent; and perhaps
  easier for both if done in the manager.
  - The chance for a "timeout" is much greater if done in the agent.
    Thus no info.
  - Given the effort and timeout considerations, this should not
    done in the agent.
Leo

---

From: Bob Clouston <[email-masked]>
Date: Wed, 25 Oct 95 11:02:11 EDT

>     the local tg table (from trs) will only have an entry if

Connection network definitions are not in the link table.  I am not concerned
with representing portnames or real TGs, just the virtual TGs.  I will
repeat the original question:

This object associates a local connection network definition with a port.
How do you intend to convey this information in the MIB?

The MIB needs a way to tell which port a CN definition belongs to.
The local tg portname object is the current proposal.  If you don't like
it, please suggest an alternate method.  We already considered adding the 
CN nmae to the port table but rejected it since a port can have multiple CNs.

Bob